- 3 minutes to read

Release Notes

Nodinite Pickup LogEvents Service Logging Agent

Info
Use the Nodinite Pickup LogEvents Service Logging Agent to achieve true end-to-end tracking by asynchronously fetching custom-coded Nodinite Log Events.

The Nodinite Pickup LogEvents Service Logging Agent empowers your integration landscape by reliably fetching your custom-coded Nodinite Log Events from a wide range of sources—including message brokers, file systems, and cloud storage. This approach reduces the amount of custom code you need to maintain and ensures robust, reliable logging for your solutions.

Nodinite Pickup LogEvents Service Logging Agent

graph LR subgraph "Systems Integration Solutions" roStrategy(fal:fa-lightbulb-on Logging Strategy) --> roBroker{fal:fa-brackets-curly Reusable
Generic Logging logic} roBroker --> |Nodinite JSON Log Event|roSink(fal:fa-file-export Intermediate storage ) roBroker -.-> |"The other format(s)"| ro2["Other Log destination(s)"] end subgraph "Nodinite instance" roPS(fal:fa-truck-pickup Pickup Service) -->roNI(fal:fa-cloud-arrow-down Log API) roSink --> roPS end

The diagram above illustrates how the Pickup LogEvents Service Logging Agent bridges your integration solutions and the Nodinite platform, enabling seamless, asynchronous log event collection from various sources.

When your message broker or solution lacks built-in tracking, simply produce a JSON-formatted log event and place it on a highly available intermediate storage. The Pickup LogEvents Service Logging Agent will handle the rest, ensuring your logs reach Nodinite for monitoring, analytics, and compliance.

Some real-world examples include:

The Pickup LogEvents Service Logging Agent is not a traditional Logging Agent with built-in logic. Instead, it reads Nodinite Log Events from sources like disks or queues and forwards them to the Nodinite Log API (RESTful). For high-performance, on-premises solutions, you can even bypass the Log API and write directly to the Log Database.

Features

Source Description Recommended Monitoring Agent External Link Configuration
ActiveMQ Fetch Log Events from ActiveMQ/ActiveMQ Artemis queues Message Queuing Agent Apache NMS ActiveMQ Configuration
AMQP New 6.2 Fetch Log Events from AMQP v1.0/ActiveMQ Artemis queues Message Queuing Agent AMQP.org Configuration
AnypointMQ Fetch Log Events from MuleSoft Cloudhub AnypointMQ platform Message Queuing Agent AnypointMQ Configuration
Azure Event Hub Fetch Log Events from EventHub; Create the Log Event using the Nodinite Serilog EventHub sink Azure Monitoring Agent EventHub Configuration
Azure ServiceBus Fetch Log Events from Azure Service Bus; Create the Log Event using the Nodinite Serilog ServiceBus sink Message Queuing Agent Azure Service Bus Configuration
Azure Blob New 6.2 Fetch Log Events from Azure Storage Account Azure Monitoring Agent Azure Blob Storage Configuration
Disk / Folder Fetch Log Events from file folders and SMB enabled shares; Create the Log Event using the Nodinite Serilog File sink File Monitoring Agent Configuration
Microsoft MSMQ Fetch Log Events from Microsoft MSMQ Message Queuing Agent Configuration
Microsoft SQL Server Fetch Log Events from Microsoft SQL Server Database Monitoring Agent Configuration
PostgreSQL Fetch Log Events from PostgreSQL database instances Database Monitoring Agent PostgreSQL Configuration

Info
Missing a source? Contact our support at support@nodinite.com and we will build it for you.

The agent performs logging by sending an HTTP/HTTPS POST of a Log Event to the api/LogEvent/LogEvent endpoint. For high-performance, on-premises solutions, you can bypass the Log API and write Log Events directly to the Log Database using multiple threads.

Frequently Asked Questions

Find more solutions and answers in the Troubleshooting user guide.

Why should I NOT send my Log Events directly to the LogAPI?

If you send Log Events directly to the LogAPI, your solution must handle error scenarios when Nodinite is unavailable, such as:

  • Network errors
  • Windows Server reboots or maintenance
  • Nodinite updates
  • Database disk space issues
  • Security changes
  • ...

By using the Pickup LogEvents Service Logging Agent, you reduce stress on your Nodinite instance and ensure logs are collected at a controlled pace, even during outages.

Read more about synchronous vs. asynchronous messaging in this Wikipedia article.

Next Step

Prerequisites
Install Nodinite Pickup Service
Configuring the Nodinite Pickup Service
Update

Add or manage Log Agents
Add or manage Log View
Log Views
Log Agents